Skip to content

docs: brand settings follow today's ship (Program ID, two payment cards, link parameter, attribution window) - #147

Merged
sonpiaz merged 1 commit into
mainfrom
docs/brand-settings-1016
Oct 17, 2026
Merged

sonpiaz merged 1 commit into
mainfrom
docs/brand-settings-1016

Conversation

@sonpiaz

@sonpiaz sonpiaz commented Oct 16, 2026 •

Copy link
Copy Markdown
Member

What changed

Brand-side docs follow what shipped to prod on 2026-10-16.

  • brand/settings.mdx: Business shows Program ID (read-only, Copy); Tracking has the Partner link parameter; Payments is two cards; Refer a brand includes Invite via email and the referred brands.
  • brand/quickstart/setup-program.mdx:
    • Business table gains Program ID.
    • Tracking: the Connect sheet ends with a prompt; the npm provider file is app/affitor-provider.tsx; tracker states and the Continue rule follow today's step; new Partner link parameter paragraph.
    • Payments: two cards (Stripe, Server API) with their states, no method to choose, owner-only Stripe text, the both-connected warning; the old screenshot is removed (it showed the method choice).
    • Go live: "either card" instead of "the method you chose"; the PageMeta prerequisite says connecting Stripe needs the owner.
  • Program ID location (Settings > Program settings > Business): glossary, 8 integration pages, tracking quickstart.
  • Attribution window: errors.mdx names the setting attribution_window_days (shown as Attribution window); inviting-partners says attribution window.
  • ?via= next to ?aff=: attribution (cookie section and scenario table), click-tracking, tracking-overview, glossary, public/docs/skill.md.

Not in this PR:

  • CLI --cookie-duration writes only cookie_window_days, which tracking never reads (CMS src/api/cli/services/cli.ts:78): brand/cli/* still says default 90. Needs a product decision first.
  • Team roles (Owner/Admin/Member/Viewer) are not documented yet.
  • A new Payments screenshot is follow-up media (setup-payments.png is no longer referenced).

No terms or money wording changes.

Why

Docs should describe the shipped brand setup flow, requested by the product team.

How verified

Labels were verified in the prod JS chunks ("Program ID", "Attribution window"). Sources (affiliate-dashboard origin/main 0b3d39dd, affiliate-cms origin/main 0f7bbaa0):

  • Program ID: dash#711 src/components/AffiliateManagement/Advertiser/Setup/BusinessStep.tsx:234-252.
  • Payments: dash#680 Setup/PaymentsStep.tsx:51-80 (two cards, done when either), :223-224, :233, :248, :255, :266, :274,277, :306 (both warning), :325.
  • Tracking: dash#691 Setup/TrackingStep.tsx:143,153-165,231-234,259-267; Mcp/ConnectSheet.tsx:67-74,170; src/lib/trackerSnippets.ts:49-60.
  • Partner link parameter: dash#674 Setup/LinkParamField.tsx:92-111; CMS src/utils/partner-link.ts:14-28 (LINK_PARAM_VIA_SINCE = 2026-10-16T00:00:00Z, older programs locked to aff); tracker public/js/affitor-tracker.js:126-133 (aff, else via). The npm SDK 2.1.3 loads the same hosted tracker.
  • Attribution window: dash#712; CMS src/api/affiliate-commission/services/attribution-window.ts:21,36-40 (attribution_window_days, default 60); click response cookie_window_days carries the effective value (affiliate-tracking/controllers/v1-tracking.ts:597-611).

🤖 Generated with Claude Code

…ds, partner link parameter, attribution window

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
affitor-docs Ready Ready Preview Oct 16, 2026 11:57pm UTC

Request Review

@sonpiaz
sonpiaz merged commit 130c98f into main Oct 17, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
Preview — 15766ad4 Deployed Oct 16, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant